HCL
Skip to main content  
 
   


SPRTechnote


"LEI Administrator Error... Invalid DataType..." when Using ODBC Driver for SQL 7.0

Technote Number: 1102988


Problem:
This issue was reported to Lotus Quality Engineering and has been addressed in
Domino 5.0.3.

Excerpt from the Partial Fix List (as of 7/25/00) for Lotus Notes and Domino
Release 5.0.3 QMR:

SPR# SPES4ESR8R - Fix "Invalid Data Type" error when using ODBC driver for SQL
7.0 while browsing metadata. [5.0.3]

As a workaround, enter the table name manually, or you can use an SQL Server
6.0/6.5 client. (Even though normally, LEI/NotesPump and DECS require that
client and server be the same version.)Supporting Information:

Brief Explanation of the Behavior:

SQL Server 7.0 supports Unicode data types and is implemented using unicode for
table, field, and other internal names (metadata). Support for Unicode in
SQLServer will come out with the native SQLServer connector, or a "future"
(date TBD) version of the ODBC connector which supports ODBC 3.5.

Brief Description of the temporary workaround:

SQL Server 7.0 supports SQL Server 6.0/6.5 clients, and these client versions
had no Unicode support. Using an SQL Server 6.5 client will cause SQL Server
7.0 to not "speak" Unicode and the ODBC connector will work.

Software Versions Required for the Workaround:

Server: SQLServer 7.0 (the problem would not occur with SQLServer 6.5)
Client: SQLServer 6.5 Client
Merant ConnectODBC version 3.5 for Win9XNT

Detailed Client Configuration for the Workaround:

Merant ConnectODBC Version 3.5 for Win9xNT

Create the datasource using the "MERANT 3.50 32-Bit SQL Server 6" ODBC driver.
Specify Data Source Name, Server Name and Database Name. Otherwise, default
settings may be used. Use this datasource when creating the connection in LEI
or DECS.
Related Documents:

More >





  Document options
Print this document
Print view

  Search
Search Advanced Search


  Fix list views

 RSS feeds   RSS
Subscribe to the fix list

  Resources
Using this database
View notices

  HCL Support
HCL Support


    About HCL Privacy Contact